Repository navigation
ci(windows): Authenticode-sign releases through Azure Artifact Signing - #160
Merged
Merged
Conversation
Tauri signs the app exe and installers through scripts/windows-sign.ps1 (bundle.windows.signCommand from a CI-written --config), and a verify step checks the installers and every exe the MSI installs. Off until the repository variable WINDOWS_SIGNING is true. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Authenticode-signs the Windows release through Azure Artifact Signing (shared account
halterio-signing, profilepublic-trust).Signs
strand.exeand the MSI (Tauri sign command),strand-cli.exe(bundled as a resource, so signed inbuild-companion.mjs), and the separately downloadedstrand-azdo.exehelper before it is archived and hashed. The helper is built in its own step, so its dependency build scripts never see the credentials.check-release-security.mjsnow requires this wiring;docs/packaging.mddocuments it. The Store MSIX route is unchanged.scripts/windows-signing-client.ps1: fetchesMicrosoft.ArtifactSigning.Client1.0.128 (SHA-256 pinned), writes the account metadata, and writes a Tauri config settingbundle.windows.signCommandtoscripts/windows-sign.ps1, passed totauri-actionas--config.scripts/windows-sign.ps1: newest Windows SDK SignTool + the dlib + Microsoft's timestamp server, then fails unlessGet-AuthenticodeSignatureisValid..exethe MSI installs (administrative install unpack), must have valid signatures.WINDOWS_SIGNING == 'true', which isn't set: until the certificate profile exists (identity validation pending in Azure), releases build exactly as before.strand-release-signingwith only the Certificate Profile Signer role; secretsAZURE_SIGNING_CLIENT_ID/AZURE_SIGNING_TENANT_ID/AZURE_SIGNING_CLIENT_SECRETare already set (expire 2028-11-11).Not run on Windows yet: the PowerShell parses cleanly and actionlint passes;
pnpm release:check-securitypasses.🤖 Generated with Claude Code